5.3.3 APPX Application Design Manual

+ Chapter 1-1: Overview of Application Design
+ Chapter 1-2: Getting Started
+ Chapter 1-3: Data Dictionary
+ Chapter 1-4: Understanding Process Design
+ Chapter 1-5: Interprocess Communication
+ Chapter 1-6: Customizing Your Application
+ Chapter 1-7: The Documentation Facility
+ Chapter 1-8: Application Design Tools
+ Chapter 2-1: Data Dictionary Overview
- Chapter 2-2: Data Dictionary Concepts
+ Chapter 2-3: Domains
+ Chapter 2-4: Files and Fields
+ Chapter 2-5: Work Fields
+ Chapter 3-1: Overview of APPX Processes
+ Chapter 3-2: Getting Started
+ Chapter 3-3: Process Definition
+ Chapter 3-4: Menu Processes
+ Chapter 3-5: Job Processes
+ Chapter 3-6: Input Processes
+ Chapter 3-7: Output Processes
+ Chapter 3-8: Update Processes
+ Chapter 3-9: Query Processes
+ Chapter 3-10: Inquiry Processes
+ Chapter 3-11: Status Processes
+ Chapter 3-12: Subroutine Processes
+ Chapter 3-13: Table Processes
+ Chapter 3-14: Automatic and Optional Children
+ Chapter 3-15: Using the Image Editor
+ Chapter 3-16: Using GUI Features of the Image Editor
+ Chapter 3-17: Using Event Points
+ Chapter 4-1: ILF Integration
+ Chapter 4-2: True/False Status Indicators
+ Chapter 4-3: Specifying Statements
+ Chapter 4-4: The ILF Editor
+ Chapter 4-5: The Appx ILF Debugger
+ Chapter 4-6: ILF Keyword Reference
+ Chapter 4-7: Predefined Fields
+ Chapter 4-8: Runtime Subroutine's and Predefined Processes
+ Chapter 4-9: Appx Chart Director API

Chapter 2-2: Data Dictionary Concepts

Application Integration Issues


APPX applications operate as part of an integrated system of applications or stand alone, depending upon the specific requirements of each installation and application. You design integrated applications as if they will always be installed as a system.

When you first process a dictionary that includes one or more fields which reference domains in outside applications, your system must include the applications that contain the domains referenced. During processing, the field stores an internal copy of the specifications entered for the domain it references. Validation and token tables are also copied at this time.

After processing the data dictionary, the application can be installed as a stand-alone. When this stand-alone application is executed, the internal copy of the referenced domain's attributes are used, not the attributes in the referenced application. You can process a stand-alone application without reinstalling the referenced applications; APPX assumes the referencing fields do not require processing.

If the domain that is referenced by a field changes, and it is necessary to incorporate those changes in the field, you must reinstall the referenced domain's application. Processing the data dictionary then updates the internal copy of the specifications for that field.

 

Application Design Manual                                         "Powered by Appx Software"

137

©2006 By APPX Software, Inc. All Rights Reserved